home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
bbsutil
/
clbkv372.zip
/
CALLBK.DOC
< prev
next >
Wrap
Text File
|
1994-03-01
|
23KB
|
545 lines
┌───────────────────────────────────────────────────────────────┐
│ W E L C O M E to... MYCALBK version 3.72 │
│ │
│ The callback verifier door for RBBS-PC sysops and │
│ │
│ finally other BBS's as well. │
│ │
│ │
│ Copyright (c) 1991-1994 SteveSoft Software. USA. │
│ │
│ All Rights Reserved. │
│ │
└───────────────────────────────────────────────────────────────┘
There has long been a need for a dedicated call back verification
program for RBBS sysops. Until now, there were a few that were
relatively well programmed, however, after having tried two or three of
them, and after having determined that they didn't quite meet my
expectations, I felt it necessary to create one. The result is the
program that you, the RBBS sysop, will shortly have fully operational on
your system.
RBBS has long had the ability to allow the use of a verification door
built-in, or more accurately, a registration door. This program, MYCALBK
takes full advantage of that RBBS ability.
***
MYCALBK now supports a multitude of BBS systems! Please read on.
***
MYCALLBK is small, fast, and above all, reliable. It will run on any IBM
system, or compatible computer on which you operate your RBBS (or any
other BBS MYCALBK currently suports). MYCALBK will detect DesQview and
give up time slices accordingly. Also, it will detect a paper out
condition if you are printing your logs and continue without "hanging"
the system.
It will take some time for you to edit the sysop configurable files
which are described in more detail later in this documentation. Other
than that, it should be fully operational on your system in about 15
minutes!
In RBBS-PC v17.3C, and RBBS v17.4 CONFIG PARAMETER 107 is used to tell
RBBS-PC what the door name is to check new users at log-in. For example,
I use "F:\RBBS\DOORS\VALIDATE.BAT"
CONFIG PARAMETER 108 is the parameter to tell RBBS-PC "This security
level AND lower, must be sent to the above named door". For example, I
have it set to level 30. Everyone is at level 30 on my RBBS until they
are called back with the verifier. The verifier can easily be setup to
increase the callers' security level when a given caller has responded
successfully to the callback question, and has been logged back into
your BBS.
For other BBS's, please follow thier instructions on how to setup a
validation door. If your system does not support auto-verifying, then
please set MYCALBK up as a regular and instruct your users that they
must execute this door before being able to have access to your system.
Installation of MYCALBK is pretty much straight forward and should cause
no difficulty for most experienced sysops. If you are a 'freshman' BBS
sysop, I strongly suggest that you read this entire document to obtain
maximum performance of the CALLBK program. The following describes the
required files and their purposes.
The batch file needed to call CALLBK from RBBS...
──────────────────────────────────────────────────
You can name the following as CALLBACK.BAT just as a reference when you
are looking through the dozens of BAT files on your system. This
example is for an RBBS system. If your system requires a different
approach or different settings, please refer to your BBS documentation.
────────────────────────
The VALIDATE.BAT file...
────────────────────────
@echo off
cd
\rbbs\doors\mycalbk
Mycalbk %1
cd \rbbs
:DONE
The VERx file is a SEMAPHORE file to allow you to create an Auto-welcome
message for your new user. I use MSGFORM.EXE (for RBBS) but you may
use something different, OR process the new user differently. Possibly
"tossing" the user into another door (Now that you know they are who
they say the are).
TIPS:
1). Do not use a .BAT file named VERIFY as DOS will not execute it.
(VERIFY is a DOS keyword.)
2). If you are using WATCHDOG or some sort of carrier watchdog,
DISABLE it when running this program! This program DISCONNECTS the
caller in order to call back. If you have WATCHDOG (or a similiar
program) enabled, watchdog will REBOOT your machine instead of MYCALBK
calling back.
───────────────────────────────────────────────────────
The Configuration files and samples...
───────────────────────────────────────────────────────
────────────
MYCALBKx.CFG (Where 'x' = node number).
───────────
F:\rbbs
YELLOW
F:\bulletin\b1
ATE1V1Q0X4
00000
Line 1 = Path to your Drop file. DORINFOx.DEF, DOOR.SYS, etc...
Line 2 = Background Color of "desktop". (BLACK or BLUE not recommended!).
Line 3 = RESERVED
Line 4 = MODEM init string to get "OK" out of it.
Line 5 = Registration code. The five (5) zeros * MUST * be there!
When you register MYCALBK you will receive a registration key which you
type in place of the five (5) zeros. The five zeros simply put a small
message on the monitor that this copy is not registered. When you do
get around to registering, I will send you a registration key which will
then put a message on the monitor that you have registered this copy,
along with the name of your BBS. Please see the information about
registering near the end of this document.
──────
SL.CFG * NOTE * SL.CFG is: Security level configuration.
────── If you do not have a security listed
30,60,30 here, MYCALBK will NOT upgrade thier
65,65,65 security.
60,60,30
Parameter 1 = ENTRANCE security (what they will be when they get here).
Parameter 2 = PASS security (what to upgrade to if they pass).
Parameter 3 = FAIL security (what to drop them to if they fail).
────────
LDSL.CFG * NOTE * LDSL.CFG is: Long distance security level cfg.
────────
30,61,30
65,65,65
Parameter 1 = ENTRANCE security (What they will be when they get here).
Parameter 2 = PASS security (what to upgrade to if they pass).
Parameter 3 = FAIL security (what to drop them to if they fail).
If you enable LD calls, you MUST have this file. Otherwise your callers
SECURITY LEVEL will be set to 0 (zero) when they return. It allows you
to "bump up" LONG DISTANCE callers so they have more time on-line (Some
SysOps prefer their long distance callers to have an extra 15 minutes
on-line. After all, they are calling long distance to visit your BBS).
If you do not like that, then just set it the same as SL.CFG.
────────────
AREACODE.CFG
────────────
803,0000,2359,1
919,1800,0800,1
Parameter 1 = areacode approved for call back.
Parameter 2 = time to START (LONG DISTANCE) call backs.
(no colons, 24hr time!).
Parameter 3 = time to STOP (LONG DISTANCE) call backs.
(no colons, 24hr time!).
Parameter 4 = hang up flag. 1 = hang up after verify.
0 = stay on the line (at YOUR expense!).
First areacode *MUST* be YOUR area code! Don't make an error here!
(Please note, if the supplied AREACODE.CFG file does not contain all
United States areacodes, please let me know so I may add them in future
releases).
*NOTE*
If you only wish to call local users back, use 0000 as your
start time and 0000 as your stop time. MYCALBK will only call
LONG DISTANCE between those 2 times.
────────────
LCLXCHNG.CFG *NOTE* LCLXCHNG.CFG is: Local exchanges cfg.
────────────
393
332
669
665
Local exchanges are ones that do NOT require